Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @matthewjasper (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

Please see the contribution instructions for more information.

Hmm, according to the CI, my fix doesn't work for macro invocations (so I made this PR drafted for now). But perhaps is it expected behavior? In fact, take the following as an example:

macro_rules! foo {
    ($i:ident) => {
        let $i = 42;
    };
}

fn main() {
    #[allow(unused_variables)]
    foo!(a);
}

#[allow(unused_variables)] in the above example doesn't suppress the lint diagnostic:

warning: unused variable: `a`
 --> src/main.rs:3:13
  |
3 |         let $i = 42;
  |             ^^ help: if this is intentional, prefix it with an underscore: `_a`
...
9 |     foo!(a);
  |     -------- in this macro invocation
  |
  = note: `#[warn(unused_variables)]` on by default
  = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

warning: 1 warning emitted

However, if the attribute is appended to main function like:

macro_rules! foo {
    ($i:ident) => {
        let $i = 42;
    };
}

#[allow(unused_variables)]
fn main() {
    foo!(a);
}

then it does suppress the lint!
So I'm wondering if I should take macro invocations into account in this PR or not... 😕

For now, I just deleted a test for macro invocation from issue-81522.rs. Please let me know if macro invocations should also be covered.

@bors r+

📌 Commit 06b3636 has been approved by matthewjasper

⌛ Testing commit 06b3636 with merge 39eee17...